-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(dex): use postgresql as backend #839
base: main
Are you sure you want to change the base?
Conversation
cmd/greenhouse/main.go
Outdated
flag.StringVar(&pgDB, "database", os.Getenv("DB_NAME"), "Database name") | ||
flag.StringVar(&pgHost, "dbHost", os.Getenv("DB_HOST"), "Database host") | ||
flag.Uint16Var(&pgPort, "dbPort", 5432, "Database port") | ||
flag.StringVar(&pgUser, "dbUser", os.Getenv("DB_USER"), "Database user") | ||
flag.StringVar(&pgPasswd, "dbPassword", os.Getenv("DB_PASSWORD"), "Database password") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The description is quite broad. I think in this case we can make it more specific and prefix with Dex e.g. "Dex Database name". Just to avoid confusion on what the DB is for.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isnβt it better if these credentials came from a secret instead of args? The deployment can then set it as env variables instead.
The connection to DB can be opened during appStart / main and the client can be passed along.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done, the password would come from a secret, but since the underlying helm chart is not yet uploaded I can not include it here.
Description
What type of PR is this? (check all applicable)
Related Tickets & Documents
Added tests?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Added to documentation?
Checklist